<p translate>
  Members are the actual IP addresses that will receive traffic from the load balancer. Each
  member must have a unique combination of IP address and port.
</p>
<p translate>
  The Available Instances table contains existing compute instances that can be added as members
  of the pool. Use the "Add external member" button to add a member not found in the Available
  Instances table.
</p>
<p>
  <strong translate>IP address:</strong>
  <translate>
  The IP address of the member to receive traffic from the load balancer. Must be a well-formed
  IPv4 or IPv6 address.
  </translate>
</p>
<p>
  <strong translate>Subnet:</strong>
  <translate>
  The network which contains the IP address of the member.
  </translate>
</p>
<p>
  <strong translate>Port:</strong>
  <translate>
  The port on which the member listens for traffic. Must be a number from 1 to 65535.
  </translate>
</p>
<p>
  <strong translate>Weight:</strong>
  <translate>
  The weight of a member determines the portion of requests or connections it services compared
  to the other members of the pool. A higher weight means it will receive more traffic. Must be
  a number from 1 to 256.
  </translate>
</p>
<p>
  <strong translate>Monitor Address:</strong>
  <translate>
  An alternate IP address used for health monitoring a backend member.
  Default is null which monitors the member address.
  </translate>
</p>
<p>
  <strong translate>Monitor Port:</strong>
  <translate>
  An alternate protocol port used for health monitoring a backend member.
  Default is null which monitors the member protocol port.
  </translate>
</p>
<p>
  <strong translate>Backup:</strong>
  <translate>
  Is the member a backup? Backup members only receive traffic when all
  non-backup members are down.
  </translate>
</p>
